-
Notifications
You must be signed in to change notification settings - Fork 249
fix: Mark WindowExec as incompatible [WIP]
#2736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2736 +/- ##
============================================
+ Coverage 56.12% 58.63% +2.50%
- Complexity 976 1460 +484
============================================
Files 119 162 +43
Lines 11743 13919 +2176
Branches 2251 2367 +116
============================================
+ Hits 6591 8161 +1570
- Misses 4012 4564 +552
- Partials 1140 1194 +54 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| // https://github.com/apache/datafusion-comet/issues/2737 | ||
| // case _: WindowExec => true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the fix for #2737
WindowExec as incompatible
WindowExec as incompatibleWindowExec as incompatible [WIP]
|
will create new version |
Which issue does this PR close?
Need to merge #2741 first
Rationale for this change
Once #2741 is merged, we can implement
getSupportLevelforWindowExecand remove the hard-coded fix that previously disabled this operator.What changes are included in this PR?
WindowExectoopSerdeMapwindowExprToProtofromQueryPlanSerdetoCometWindowCometSinkclassWindowExecas as sink to work around org.apache.comet.CometNativeException: assertion failed: !self.format.is_null() #2737 (I do not understand what the root cause was though)How are these changes tested?